Summary

• Improve the generated report Interpretation copy so REVIEW explains warnings in plainer language.
• Regenerate the included page 006 and page 012 example reports and update the README excerpt.

Why

• The report should help a reader understand why REVIEW was selected before external human-readability review.

What

• Preserve checks, counts, IDs, statuses, details sections, section order, CLI behavior, decisions, and exit codes.
• Make the Interpretation wording clearer for content/noise, text-usefulness, and ambiguous image findings.
• Keep technical evidence in Noise / Layout Signals and check detail sections.

Tests

• .venv/bin/python -m pytest -p no:cacheprovider tests
• .venv/bin/python -m ruff check src tests
• .venv/bin/python -m pdf_quality_report.report --help
• git diff --check
• rg -n "Users/|private/tmp|Development/" README.md docs examples

Risks

• Low: wording changes may still need refinement after external readability feedback.

Rollback

• Revert this PR to restore the previous Interpretation wording and generated examples.